Skip to content

Conversation

sergey-semenov
Copy link
Contributor

@sergey-semenov sergey-semenov commented Oct 8, 2025

With the introduction of DeviceKernelInfo, assert usage and implicit local argument information is now duplicated in program manager. This patch removes the duplicate maps and makes it so that device kernel info map is filled out during image registration, with the compile time information added when it's available (during the first submission of the kernel).

Additinally, this patch ensures that device kernel info instances are added to the program manager only during image registration, and gets rid of entries from other sources that polluted the map.

With the introduction of DeviceKernelInfo, assert usage and implicit local
argument information is now duplicated in program manager. This patch removes
the duplicate maps and makes it so that device kernel info map is filled out
during image registration, with the compile time information added when it's
available (during the first submission of the kernel).
Comment on lines +244 to +246
return MOwnsDeviceKernelInfo
? MDeviceKernelInfo
: ProgramManager::getInstance().getDeviceKernelInfo(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we just have a reference/pointer as the member (potentially pointing to the owning smart pointer member) instead of doing those lookups?

Copy link
Contributor Author

@sergey-semenov sergey-semenov Oct 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we should. I was planning that as a follow-up change since the lookup is already there right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants